Conversation
Currently if the credential helpers packaged with git aren't on your PATH, git will fail to locate them. This most notably affects git maintanence1 which generates systemd units / launchd agents that invoke git directly without setting PATH. Home Manager is also able to generate maintanence units for systemd and does not set PATH2, meaning credential helpers will not work without additional configuration. Moving the credential helpers to git's exec path3 allows git to locate them regardless of how PATH is set, and matches the packaging of Fedora4 and Homebrew5. Typically credential helpers are not added to PATH unless they are provided by another package separate from git (e.g. git-credential-gcloud). I opted to create symlinks at the old bin paths in case some users were relying on invoking them directly. In practice I doubt this is done much. If we want to slim down git's bin dir I think the symlinks could be removed, and in doing so we'd better match the packaging done in other distributions.
This was removed by upstream in <renpy/renpy@f2d3e0d>.
This isn’t used by the X11 backend anyway, which is the only one we build for macOS. Even though it has a native macOS frontend. But I don’t want to spend more time on this.
Patch needs adjusting, build process is super messed up, package is out of date and not used in Nixpkgs other than by another unused library… not worth it.
Co-authored-by: sternenseemann <sternenseemann@systemli.org>
The dependency is added correctly now since ghc-tags 1.5 and GHC 9.8 don't match, causing Cabal to resolve the flag as we'd like here.
The base bounds have been revisioned on hackage https://hackage.haskell.org/package/warp-systemd-0.3.0.0/revisions/
Not very important anymore and no longer works with the core pkg version of time shipped with >= 9.12.
The next version(s) of brillo* won't need these overrides as the dependency on bytestring has been removed in the upstream repository.
Test suites won't work correctly (or entirely) since some test data is missing from the released tarballs.
ofborg
bot
removed
the
2.status: merge conflict
github-actions
bot
added
4.workflow: staging
wolfgangwalther
removed
6.topic: nixos
1 task
Upstream version is 10.0p2 but Debian cut it at 10.0p1. See the note about the error in the release process: https://www.openwall.com/lists/oss-security/2025/04/09/6
This was referenced May 5, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
20 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Helpful links
https://hydra.nixos.org/job/nixpkgs/staging-next/unstable#tabs-constituents
https://hydra.nixos.org/job/nixos/staging-next-small/tested
https://hydra.nixos.org/jobset/nixpkgs/staging-next
https://hydra.nixos.org/jobset/nixos/staging-next-small
Important breakages
nothing notable so far